Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1259

reference
493-tree-1
name
1259
tree-preservation-order

undefined

493-tpo-1
uprn
address-text
point
POINT (-1.023336 50.882917)
geometry
MULTIPOLYGON (((-1.023279 50.882911,-1.023281 50.882922,-1.023289 50.882932,-1.023302 50.882940,-1.023317 50.882945,-1.023335 50.882947,-1.023353 50.882945,-1.023369 50.882940,-1.023381 50.882933,-1.023390 50.882923,-1.023393 50.882912,-1.023390 50.882900,-1.023382 50.882890,-1.023370 50.882882,-1.023354 50.882877,-1.023336 50.882875,-1.023319 50.882877,-1.023303 50.882882,-1.023290 50.882890,-1.023282 50.882900,-1.023279 50.882911)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL